Hello, what are the best practices when it comes to creating Baseline Set Definitions? Should you create them at the folder/projectlLevel, etc. What are common issues. Thank you. -Jim EHcnck - Thu Feb 13 15:47:32 EST 2014 |
Re: Baseline Set help needed! Seems to me it would be at the kind-of-module level. I think it a good idea to "baseline" all your Requirment modules at the same time as you would thus have a Requirement Baseline to target. You could later say "My software matches Requirement baseline 2.3a". Likewise perhaps baseline all your "Test" modules, which can then be said to match Requirement baseine 2.3a. -Louie |
Re: Baseline Set help needed! I would say there are two reasons for using baseline sets. 1. To baseline multiple modules at the same time, making it easier to do it from the baseline set dialog rather than opening and baslining each module by it self. 2. To maintain/save traceability between baselined modules, at the time when the modules were baselined. If all modules are baselined at the same time or not, I would say depends on if all of the modules were ready to be baselined at one time, otherwise I would think that different modules, containing different artifacts may very well be baselined into the set when they become ready/approved but only if the other modules already baselined into the set are what the newer modules are based on, ie no change has been made to them... So, I would say the strategy depends on what you want to achieve, and your work process. /sekrbo |